FSCSI Timeout Messages

When FC protocol driver sends commands to the device drive or to the adapter, a timer is stated. If the timer expires prior to receiving a response, then the FC protocol driver will log a message in the AIX Error Log. These messages indicate that one of the following has occurred:

Detail Data SENSE DATA NOTE: Below is a portion of the AIX 5.3 and AIX 6.1 error templates. Click here to see full error template
AIX Version 5 and below

RRRR RRRR AAAA AAAA BBBB BBBB CCRR RRRR RRRR YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ GGGG GGGG OOOO OOOO OOOO OOOO
EEEE EEEE
EEEE EEEE
VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV VVVV


AIX Version 6 and above

hhhh hhhh AAAA AAAA BBBB BBBB CCtt vvvv TTTT YYYY LLLL LLLL LLLL LLLL FFFF FFFF
QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ QQQQ
GGGG GGGG pppp pppp OOOO OOOO OOOO OOOO
EEEE EEEE EEEE EEEE ssss ssss ssss ssss
wwww wwww wwww wwww nnnn nnnn nnnn nnnn nnnn qqqq qqqq qqqq rrrr rrrr rrrr rrrr
Error Code
AAAA AAAA
What it means What to do
0x0000 001e The AIX protocol driver has receive a time out for an unknow Task Management command. Contact AIX support
0x0000 0020 A command time out to a target that is not open and the N_Port ID is not valid. Contact AIX support.
0x0000 0021 An open to the end device timed out.
  • This may indicate a problem in the SAN
  • If the CC field is 2, check that the switch indicates a proper connection (Fabric login is current).
  • Check that the target device is accepting a login from the source
If this issue persists, contact AIX support.
0x0000 0022 Command timer expired, but the command completed. .. This is an informational only message
0x0000 0023 The AIX protocol driver has received a command time out for a command that was not active. Contact AIX support
0x0000 0026 A IOCB or target cancel has timed out This indicates a problem in the SAN.
The target device has not responded to the ABTX/ABTSIf this issue persists, contact AIX support
0x0000 0027
0x0000 0028
0x0000 0029 The AIX protocol driver has attempted to re-establish a connection with device in the SAN and the attempt timed out This may indicate a problem in the SAN or a AIX software problem
  • If there accompanying FCS_ERR2 (0X27) this is very likely a SAN issue. Check the device associated with the device target N_PORT_ID (.EEEE EEEE EEEE EEEE)
  • If not, then Contact software support.
0x0000 002a A process or N_Port Discovery (PRLI or PDISC) has timed out This may indicate a problem in the SAN
  • If the CC field is 2, check that the switch indicates a proper connection (Fabric login is current.
  • Check that the target device is accepting a PRLI or PDISC from the sourceIf this issue persists, contact AIX support
0x0000 002b Target reset was sent and a response has not been receive by the server This is a SAN issue (switch or target subsystem)
Check the target device associated with the target devcide N_PORT_ID (.EEEE EEEE EEEE EEEE)
If this issue persists, contact AIX support
0x0000 002c
0x0000 002d The AIX protocol driver has received a command time out for an unknown timer ID, Contact AIX support
0x0000 002F The AIX protocol driver has received a command time out for an abort device command., Contact AIX support
0x0000 004f A request to a device has timed out
This is a SAN problem.
Check with the switch to verify that the Fabric login (FLOGI) to the switch and N_Port Login (PLOGI) to the name server are current for this adapters port.
Contact AIX support
0x0000 0070 The timer expired while waiting for the link to come up. This indicates a problem with the link, Do link down PD.
0x0000 0071 The timer has expired waiting for the adapter to resume. The adapter is put into the resume state during the firmware download. This may indicate a AIX, system or adapter problem
If the adapter does not come available following firmware download,
Check the error log for FCS_ERR2 error 0x0000 0026 (Mailbox time out). this may indicates that the adapter did not come out of reset and may have had the firmware image corrupted during the firmware download. If the adapter does not become available following and IPL of the server or partition, then it may need to be replace. (In the past, these problems have been caused by the System firmware or the device driver).
If the adapter does become available following an IPL, then the problem is usually in device driver firmware download routines and the adapter does NOT need to be replaced.